Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@apps/api/src/bid-screening/http-schemas/bid-screening.schema.ts`:
- Around line 14-31: The StorageResourceSchema currently allows any
attributes[].key but must enforce the same provider-inventory SDL key format;
update validation so AttributeSchema.key (or the attributes array validation
inside StorageResourceSchema) matches the provider-inventory SDL key pattern
(use the exact regex/validator used in provider-inventory) and return Zod issues
on the specific attribute key (path like ["attributes", i, "key"]) with a clear
message when it fails; ensure the change reuses AttributeSchema if possible so
other schemas stay consistent and preserve OpenAPI metadata.

In
`@apps/provider-inventory/src/lib/hydrate-cluster-state/hydrate-cluster-state.ts`:
- Around line 16-43: The hydration functions assume well-formed input and can
throw when raw is malformed; make hydrateClusterState, hydrateNode and
hydratePair defensive: ensure cluster.nodes is an array before mapping (use
Array.isArray(cluster.nodes) ? cluster.nodes : []), ensure cluster.storage is a
plain object before Object.entries (fallback to {}), and in hydrateNode guard
node.gpu and node.gpu.quantity (use node.gpu?.quantity ?? 0 and node.gpu?.info ?
node.gpu.info : []) and default fields like storageClasses/cpus to [] when not
arrays; replace direct BigInt conversions in hydratePair with a safe conversion
helper (e.g., coerce to number/string then try/catch BigInt or default to 0) so
BigInt(pair.allocatable) and BigInt(pair.allocated) never throw on malformed
inputs.

In
`@apps/provider-inventory/src/repositories/bid-screening/bid-screening.repository.integration.ts`:
- Line 12: Replace the relative import of the repository with the backend source
path alias: change the import line that currently brings in AUDITOR and
BidScreeningRepository from "./bid-screening.repository" to use the `@src/`* alias
(e.g., import { AUDITOR, BidScreeningRepository } from
"@src/repositories/bid-screening/bid-screening.repository"), updating the module
specifier so the test uses the aliased backend source path.

In
`@apps/provider-inventory/src/repositories/bid-screening/bid-screening.repository.ts`:
- Line 11: Replace the relative import of aggregateCriteria and
BidScreeningCriteria from "./bid-screening.aggregator" with the backend source
path alias import using `@src` so the file uses the project aliasing convention;
update the import statement that references aggregateCriteria and type
BidScreeningCriteria in bid-screening.repository.ts to import from the
corresponding module via the `@src/`* alias (keeping the same exported symbols and
module name bid-screening.aggregator).

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In
`@apps/provider-inventory/src/repositories/bid-screening/bid-screening.aggregator.ts`:
- Around line 46-48: The max-per-replica variables (maxPerReplicaCpu,
maxPerReplicaMemory, maxPerReplicaGpu) are being updated even for entries with
count === 0; change the comparisons so they only update when the item’s count is
greater than zero (e.g., guard the existing checks with count > 0), so use
conditions like if (count > 0 && cpu > maxPerReplicaCpu) and similarly for
memory and gpu to avoid zero-count entries inflating the maxima in the
aggregation logic in bid-screening.aggregator (variables: cpu, memory, gpu,
count, maxPerReplicaCpu, maxPerReplicaMemory, maxPerReplicaGpu).

---

Nitpick comments:
In
`@apps/provider-inventory/src/repositories/bid-screening/bid-screening.aggregator.spec.ts`:
- Line 5: The test import currently uses a relative path; update the import in
bid-screening.aggregator.spec.ts so it uses the backend source alias (e.g.,
replace the relative import of aggregateCriteria from
"./bid-screening.aggregator" with the `@src/`* alias equivalent) to conform to
backend rules; ensure the import still references the same exported symbol
aggregateCriteria and that any test runner/tsconfig path mappings already
support the `@src` alias.
- Around line 26-31: The test "count=0 contributes nothing to totals" should
also assert that per-replica maxima remain zero: update the spec that calls
aggregateCriteria([makeUnit({... count: 0 })], makeRequirements()) to include
expect(c.maxPerReplicaCpu).toBe(0n), expect(c.maxPerReplicaMemory).toBe(0n) and
expect(c.maxPerReplicaGpu).toBe(0n); this ensures aggregateCriteria's
max-per-replica behavior for the zero-count unit (referenced symbols:
aggregateCriteria, makeUnit, makeRequirements) is locked in and will catch
regressions.